Skip to content

Conversation

@oliverw1
Copy link

@oliverw1 oliverw1 commented Oct 1, 2025

The REPL output now matches the instructions.

Extra info has been added to aid with the explanation as well for those who are not aware of DST, particularly the exact change happening that day.

The REPL output now matches the instructions. Extra info has been added
to aid with the explanation as well for those who are not aware of DST.
@codspeed-hq
Copy link

codspeed-hq bot commented Oct 1, 2025

CodSpeed Performance Report

Merging #920 will not alter performance

Comparing oliverw1:docs/fix-fluent-helpers-example (0e32103) with master (3382956)

Summary

✅ 1 untouched

@ashb
Copy link
Member

ashb commented Oct 22, 2025

Re-triggering CI.

@ashb ashb closed this Oct 22, 2025
@ashb ashb reopened this Oct 22, 2025
>>> dt = dt.in_tz('Europe/Paris')
>>> dt = dt0.in_tz('Europe/Paris')
>>> print(dt)
'2013-03-31T04:30:00+02:00'
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Something weird is going on here. How is this possible that dt0.set(tz=...) produces different result than dt0.in_tz(...) for the same timezone?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in_tz converts the time to the new timezone. set normally doesn't convert the time, just sets the timezone, but presumably when the time is invalid in the new time zone it has to change it to a valid one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants